Skip to content

Comments

1165 build separate knowledge flow images for offline and online use cases#1170

Draft
simcariou wants to merge 4 commits intomainfrom
1165-build-separate-knowledge-flow-images-for-offline-and-online-use-cases
Draft

1165 build separate knowledge flow images for offline and online use cases#1170
simcariou wants to merge 4 commits intomainfrom
1165-build-separate-knowledge-flow-images-for-offline-and-online-use-cases

Conversation

@simcariou
Copy link
Collaborator

No description provided.

@simcariou simcariou marked this pull request as draft February 18, 2026 10:00
@gitguardian
Copy link

gitguardian bot commented Feb 23, 2026

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
17205519 Triggered Generic Password 44468f6 deploy/local/k3d/values-local.yaml View secret
27366443 Triggered Generic Password 44468f6 deploy/local/k3d/values-local.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@simcariou simcariou force-pushed the 1165-build-separate-knowledge-flow-images-for-offline-and-online-use-cases branch from a50a0c9 to 761297a Compare February 23, 2026 08:56
@simcariou simcariou force-pushed the 1165-build-separate-knowledge-flow-images-for-offline-and-online-use-cases branch from 761297a to e74829d Compare February 23, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build separate knowledge-flow images for offline and online use cases

1 participant